Skip to content

[UI] [VAULT-37770] Update vault-reporting addon to remove the survey link - #31225

Closed
erentantekin wants to merge 1 commit into
mainfrom
ui/VAULT-37770
Closed

[UI] [VAULT-37770] Update vault-reporting addon to remove the survey link#31225
erentantekin wants to merge 1 commit into
mainfrom
ui/VAULT-37770

Conversation

@erentantekin

@erentantekin erentantekin commented Jul 8, 2025

Copy link
Copy Markdown
Contributor

Description

[UI] VAULT-37770 [Generated PR] Remove survey link

This PR updates vault-reporting with the latest state of the shared-secure-ui repo. The main purpose of this syncing is to remove the non-functional qualtrics survey link from vault usage dashboard.

This PR is auto-generated with a script from shared-secure-ui repo.

TODO only if you're a HashiCorp employee

  • Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
    • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
  • ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
    of a public function, even if that change is in a CE file, double check that
    applying the patch for this PR to the ENT repo and running tests doesn't
    break any tests. Sometimes ENT only tests rely on public functions in CE
    files.
  • Jira: If this change has an associated Jira, it's referenced either
    in the PR description, commit message, or branch name.
  • RFC: If this change has an associated RFC, please link it in the description.
  • ENT PR: If this change has an associated ENT PR, please link it in the
    description. Also, make sure the changelog is in this PR, not in your ENT PR.

PCI review checklist

  • I have documented a clear reason for, and description of, the change I am making.
  • If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
  • If applicable, I've documented the impact of any changes to security controls.

Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

@erentantekin
erentantekin requested a review from a team as a code owner July 8, 2025 17:32
@github-actions github-actions Bot added the hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed label Jul 8, 2025
@erentantekin
erentantekin requested a review from j--w July 8, 2025 17:35
@github-actions

github-actions Bot commented Jul 8, 2025

Copy link
Copy Markdown

Build Results:
All builds succeeded! ✅

@erentantekin erentantekin changed the title [UI] [VAULT-37770] [Generated PR] Remove survey link [UI] [VAULT-37770] [Generated PR] Update vault-reporting addon to remove the survey link Jul 8, 2025
@erentantekin erentantekin changed the title [UI] [VAULT-37770] [Generated PR] Update vault-reporting addon to remove the survey link [UI] [VAULT-37770] [Generated] Update vault-reporting addon to remove the survey link Jul 8, 2025
@erentantekin erentantekin changed the title [UI] [VAULT-37770] [Generated] Update vault-reporting addon to remove the survey link [UI] [VAULT-37770] Update vault-reporting addon to remove the survey link Jul 8, 2025
@github-actions

github-actions Bot commented Jul 8, 2025

Copy link
Copy Markdown

CI Results:
All Go tests succeeded! ✅

@@ -0,0 +1,33 @@
/**
* Copyright (c) HashiCorp, Inc.
* SPDX-License-Identifier: BUSL-1.1

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm not sure why you have this declaration file for this. I think this is from an old test branch that never got merged so maybe the sync script needs to empty out the dis/declaration folders before generating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hashicorp-contributed-pr If the PR is HashiCorp (i.e. not-community) contributed pr/no-changelog pr/no-milestone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants